home *** CD-ROM | disk | FTP | other *** search
- Path: fn1.freenet.edmonton.ab.ca!grantb
- From: grantb@fn1.freenet.edmonton.ab.ca ()
- Newsgroups: comp.lang.c
- Subject: Free Pacific C problem
- Date: 6 Jan 1996 16:45:58 GMT
- Organization: Edmonton Freenet, Edmonton, Alberta, Canada
- Message-ID: <4cm906$l8v@news.sas.ab.ca>
- NNTP-Posting-Host: fn1.freenet.edmonton.ab.ca
- X-Newsreader: TIN [version 1.2 PL2.3]
-
- Firat off, I'd like to say that the Pacific C package is a nice little
- integrated environment for doing software for DOS (especially since the
- evaluation cost id nothing!). There are a few unfortunate problems when
- mixing stream i/o with console i/o (problems beyond what one would
- experience in Turbo C), but my biggest frustration is with the debugger.
-
- It could be that I don't understand what this debugger is supposed to do,
- but from the help menu it looks like it should be able to single-step
- code at the C source level. All I get is assembly level. Several of the
- commands respond with a "no source loaded" message implying that the
- source or debugging info isn't getting loaded.
-
- Well, I'm turning ON the debug info flag and I don't see any explicit
- command from within the debugger to load said source, so I'm stumped!
-
- Anyone have any ideas??? I've contacted hitech.com.au, but the only
- response I got was a statement of the obvious. Is there anything else
- (obvious or not), anyone can think of?
-
- GB
-